Systems and methods for navigating a calendar

ABSTRACT

Methods, systems, and graphical user interfaces are provided for navigating a calendar application executing on a computer system. Aspects of scrolling by day and scrolling by week are combined into a hybrid approach that includes advantages of both. For example, the week can be displayed with the current day first (e.g. in the left most column), thereby providing a more relevant view to a user. Then, when a user selects to move forward or backward, the next or previous full week (i.e. starting with a designated day, such as Sunday or Monday) can be displayed. And, when a user forward through the current day (or other selected day), the week view can stop with the selected day displayed first, to give a user a view of the next set of days following the selected day.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is related to commonly owned and concurrently filedU.S. patent application Ser. No. 13/366,230, filed Feb. 3, 2012, thedisclosure of which is incorporated by reference in its entirety.

BACKGROUND

The present application relates generally to a calendar applicationrunning on a computer system, and more specifically to navigating howthe calendar will move forward and backward while in a week view.

Typical calendar applications allow a user to view a week at one time.The week view is a fixed display in that the week is always displayedwith Sunday being first or Monday first, if only a workweek isdisplayed. These calendar applications often have two methods ofnavigating in the week view: 1) scroll one week at a time or 2) scrollone day at a time. Both the fixed display and limited navigation make itdifficult to see relevant events on a same page or easily navigate to adesired view.

Therefore, it is desirable to have improved methods, systems, andgraphical user interfaces for navigating in a week view of a calendar.

BRIEF SUMMARY

Embodiments provide methods, systems, and graphical user interfaces fornavigating a calendar application executing on a computer system. Forexample, a navigation object can be used to advance the days displayedin a week view of a calendar window until a selected day (e.g. today) ora start day of a week is displayed first in the sequence of days.

According to one embodiment, a method of navigating a calendarapplication executing on a computer system is provided. A first week isdisplayed in a calendar window on a display of the computer system. Aweek is a set of N sequential days with N being an integer greater thantwo. A selection of a day in the first week is received, where theselected day is not displayed first in the sequence of N days in thecalendar window. A user provides input to advance the calendar window bya week. The calendar window advances by less than N days such that theselected day is displayed first in the sequence of N days in thecalendar window.

According to another embodiment, a graphical user interface (GUI) isprovided for navigating a calendar application executing on a computersystem, the GUI being generated by one or more processors of thecomputer system. A calendar window has in a week view that displaysevents for N sequential days, with N being an integer greater than two.The week view has a boundary day that defines a start of any week. Afirst of one or more navigation objects is used for navigating whichdays are displayed in the calendar window while in the week view. Thefirst navigation object is configured to advance the days displayed inthe calendar window until the boundary day is displayed first in thesequence of N days. The first navigation object is also configured toadvance the days displayed in the calendar window until a selected dayis displayed first in the sequence of N days. The boundary day and theselected day are independently determined.

Other embodiments are directed to systems and computer readable mediaassociated with methods described herein.

A better understanding of the nature and advantages of the presentinvention may be gained with reference to the following detaileddescription and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A shows a calendar window of a calendar application that may beimproved with embodiments of the present invention. FIG. 1B showscalendar window with a different time range.

FIG. 2A shows a graphical user interface (GUI) for viewing a calendarapplication according to embodiments of the present invention. FIGS.2B-2D show graphical user interfaces (GUI) with progressively earliertime ranges for the calendar window.

FIG. 3 is a flowchart illustrating a method a method for displayingevents in a calendar application executing on a computer system.

FIG. 4 shows a graphical user interface (GUI) for viewing a calendarapplication where an event object is rotated at an edge of the calendarwindow according to embodiments of the present invention.

FIG. 5 shows a graphical user interface (GUI) for viewing a calendarapplication where an event object indicating an off-screen event ishighlighted the calendar window 500 according to embodiments of thepresent invention.

FIG. 6 shows a graphical user interface (GUI) for providing setupinformation for navigating a calendar window according to embodiments ofthe present invention.

FIG. 7 is a flowchart illustrating a method for navigating a calendarapplication executing on a computer system according to embodiments ofthe present invention.

FIG. 8A shows a calendar window of a week view starting with Sunday anda selected day of Tuesday. FIG. 8B shows a calendar window of a weekview starting with the selected day of Tuesday after being advanced witha navigation object.

FIG. 9 is a flowchart illustrating a method for determining how tochange the days displayed in a calendar window in response to a userinput according to embodiments of the present invention.

FIG. 10A shows a calendar window resulting from a forward gesture forthe calendar window in FIG. 8B. FIG. 10B shows a calendar windowresulting from a backward gesture for the calendar window in FIG. 8A.

FIG. 11 shows a block diagram of an example computer system 1100 usablewith systems, graphical user interfaces, and methods according toembodiments of the present invention.

DETAILED DESCRIPTION

Embodiments provide new features to a calendar application. One featurerelates to indicating events that are off-screen (outside of a viewabletime range). The indication uses an event object that is used torepresent an event when the event is within the viewable time range.Such a re-use of the event object can help relay additional informationbesides that some event is off-screen and can provide a seamlessinterface. Another feature relates to navigating the days shown in aweek view of a calendar. For example, when gesturing to move thecalendar forward or backward by a week, the calendar can be made to stopat the current day (or other selected day) as well as the start of theweek. As today can have particular importance for previewing the comingdays, such navigation allows a user to more quickly and easily viewimportant events in the calendar.

I. Introduction

FIG. 1A shows a calendar window 100 of a calendar application that maybe improved with embodiments of the present invention. The calendarapplication may be running on one or more processors of a computersystem and shown on a display (e.g. a compute monitor or internalimaging device) of the computer system. As shown, calendar window 100has columns 120 showing a week starting on Sunday and going to Saturday.A week may be any seven days, and may start on any day (e.g. Saturdayinstead of Sunday). The rows 110 show times within a selected timerange, which may be displayed in various formats, such as military orstandard time.

Event objects 105 are shown in the calendar window. Event objects 105correspond to events that have put entered into the calendarapplication. An event can be defined with a start time and an end timeon a particular day. A user can enter in such information in cariousways, e.g., by entering in the times with a keyboard, selecting a timewith a cursor by clicking on calendar window 100 at a particular time,or by speaking commands regarding the event and the times. A user canalso define a narrative for the event.

An event object can then be displayed to in calendar window 100 to showthe start and end time of the particular event on the particular day.For example, event object 105 a has been defined to be between 11 AM and12:30 PM on Saturday, Jan. 21, 2012. Event object 105 a shows 11 AM asthe starting time in text (although other embodiments can rely on rows110 to indicate time), along with a narrative explaining a title of theevent “Soccer game” and an explanation of where the event is at “WestField”.

Events can also be specified with just one time entered by a user. Forexample, a user can specify a start time, and a default length of timecan be used to determine the end time. Similarly, a user could identifyan end time, with the start time being define using a default. Thus,although each event does have a start and end time, a user does not haveto specify both values. In various embodiments, the default length couldbe 30 minutes, an hour, or for the rest of the day, which may be upuntil a certain time (e.g., the end of the work day or to midnight).Additionally, a user can specify that an event is all day, whicheffectively specifies the start time and an end to be predeterminedvalues, such as 8 am to 5 PM. Instead of a default value, the user canalso specify a time length.

An events can also be defined to occur on more than one day. Forexample, an event can repeat on certain days of the week or onconsecutive days. Event object 105 b which starts at 8 am and end atabout 8:45 AM on Friday, Jan. 20, 2012 corresponds to an event that alsooccurs on Monday and Wednesday at the same times. Thus, a user mayindicate multiple events through a single interface. For example, a usercan specify that the kindergarten pickup is to repeat on Monday,Wednesday, and Friday of every week.

A beginning 112 of the time range marks the time at which event objectsoccurring later are displayed at the time the corresponding eventoccurs. Event objects that occur before beginning 112 are not displayed.An ending 115 of the time range marks the time at which event objectsoccurring before are displayed at the time the corresponding eventoccurs. Event objects that occur after ending 115 are not displayed. Asshown, the time range is about 7:30 AM to about 7:30 PM. Beginning 112and ending 115 are examples of edges of calendar window 100. It ispossible that the calendar is displayed with time on the horizontalaxis, and thus the edges of the time range may appear on the left andthe right of calendar window 100 instead of at the top and the bottom.

Some event objects may be partially displayed in the time range. Forexample, event object 105 c starts at 6 PM and runs until 8 PM. But, 8PM is after ending 115 of the time range. In this case, event object 105c is displayed in the times that are visible for the current settings ofthe time range.

An all-day event can also be defined. Such an event is typicallyassociated with an event that occurs that day, but not at any specifictime, or the time is not of importance and is not specified. As shown,payday object 123 is such an all-day event. Payday object 123 is shownat the top of the Friday column, and does not appear in the displayedtime range.

FIG. 1B shows calendar window 100 with a different time range. In FIG.1B, the time range is from about 12 noon to about 12 AM. Events objects105 and 105 a are still labeled as in FIG. 1A. However, event object 105b is no longer visible in the new time range. Event object 105 b has anend time at 8:45 AM, which is before the beginning 113, which is 12noon. Thus, if one is viewing the calendar with the time rangecorresponding to beginning 113 and ending 116, a user does not know theexistence of event object 105 b.

Additionally, FIG. 1B shows two new event objects 105 d and 105 e. Eventobject 105 d has a start time of 7:30 PM, which is at the ending time115, and thus was not displayed for the time range selected in FIG. 1A.But, 7:30 PM is before ending time 116, and thus event object 105 d isdisplayed in the selected time range of FIG. 1B. Similarly, event object105 e has a start time of 10:00 PM, which is after the ending time 115,and thus was not displayed for the time range selected in FIG. 1A. But,10:00 PM is before ending time 116, and thus event object 105 e isdisplayed in the selected time range of FIG. 1B.

II. User Interface for Off-Screen Events

FIG. 2A shows a graphical user interface (GUI) for viewing a calendarapplication according to embodiments of the present invention. Thecalendar application may be running on one or more processors of acomputer system and shown on a display (e.g. a compute monitor,projector, or internal imaging device) of the computer system, as canother embodiments of calendar applications described herein. Calendarwindow 200 is laid out in a similar fashion as calendar window 100.However, event objects that are off-screen are now identified.

Calendar window 200 is shown with a viewable time range of about 12:15PM to about midnight. In some embodiments, events can span more than oneday and an event object can extend past midnight. Event object 205 a isshown displayed at beginning time 211 (about 12:15 in this case). Asshown, event object 205 a indicates that an event occurs beforebeginning time 211. Since a small part of event object 205 a isdisplayed one can identify that the event object does not simply endright after beginning time 211. In one implementation, only four pixelsin height are shown for a clipped event object, but otherimplementations could use more or less. Other embodiments describedbelow can provide greater clarity in distinguishing event objects thatend just after a beginning edge of the time range, and instances wherean off-screen event is being indicated. Event object 205 a could beshown above beginning edge 211, but such an embodiment could haveconfusion with all-day events.

If there are more than two events that end (i.e. have an end time)before the beginning edge of the selected time range, parts of two eventobjects can be shown. For example, event object 205 b and event object205 c are shown for Wednesday. Since there are two event objects, theobjects are stacked on top of each other. As shown, event object 205 bextends lower than event object 205 c. Thus, one can easily identify thenumber of events that are off-screen. In another embodiment, one eventobject (e.g., the most recent event object getting held at the edge) isdisplayed along with a number indicating the number of events that areoff-screen.

Because both objects are stacked, the two objects may appear as oneobject. To remedy this, some embodiments can shift to the right theevent object that is later in time while having that event object extendlower. For example, event object 205 b can be shift to the right (anexample of a transverse direction). If the stacked events are of adifferent calendar, the distinctions can be easier to see, as is shownin other figures. To provide greater clarity, event objects occurringearlier could be displayed in a top layer, and thus they can be seen,which is shown in later figures.

Attention is brought to event object 205 d, as it is still viewablewithin the selected time range, but will soon not be once a rangecontrol is used to move the time range up. The time range may be changedin various ways, using a range control. For instance, when a cursor(e.g., as controlled via a pointing device like a mouse) hovers over thecalendar window, a scroll wheel can be used to move the time range upand down. Other examples include: specifying the time range via text orpicklist (i.e. specifying a beginning time and an ending time), dragginga scroll bar, and swiping on a surface of the display. These featuresand others mentioned above may be implemented within embodiments of thepresent invention.

FIG. 2B shows a graphical user interface (GUI) with an earlier timerange for calendar window 200. The time range shown is between about 11AM and 11 PM, which is between beginning 212 and ending 222. As one cansee, event object 205 d is now shown at ending edge 222 to indicate thatan event starts later than the ending of the time range, i.e. about 11PM. As shown in FIG. 2A, the event object 205 d actually starts at about11:15 PM. Note that other time ranges besides about 12 hours may beused.

In one embodiment, where the time range is changed continuously (e.g. byscrolling) to later times (e.g., from FIG. 2B to FIG. 2A), event object205 d moves down calendar window 200. As the top (e.g., as signified bythe start time) of event object 205 d reaches the ending edge, eventobject 205 d can stick at the ending edge, thereby preserving thenotification of an off-screen object. As discussed later, when otherevent objects on the same day move downward, the top of each eventobject can be held at a point slightly above the highest event objectalready stuck at the ending edge.

Event object 205 e indicates that the poker game starts at about 8:15PM. If the time range ends at a time earlier than 8:15 PM, then twoevents would be off-screen, in this case, starting later than the end ofthe selected time range. Some embodiments can indicate when two eventsare off-screen, as shown in FIG. 2C.

FIG. 2C shows a graphical user interface (GUI) with an earlier timerange for calendar window 200. The time range shown is between about8:30 AM and 8:30 PM, which corresponds to beginning 213 and ending 223.As is shown, both events object 205 d and event objet 205 e aredisplayed at the ending edge 223 of calendar window 200. Specifically,object 205 e is shown stacked on top of event object 205 d, which isshown in the forefront so it can be seen. Accordingly, the fact that twoevents occur later than 8:30 PM on Saturday the 28^(th) can beidentified by a user, even when the two event objects are from a samecalendar (e.g. a blue calendar for personal events).

Event object 205 b is now fully within the selected time range of about8:30 AM to 8:30 PM. Event object 205 b is shown displayed between 10 AMand 11 AM. Thus, the previous time ranges would have informed a userthat an event occurred before 11 AM on Wednesday. Also, a user can bespecifically informed that an event on the green calendar (e.g., a workcalendar) had an ending time that is closest to the time ranges withbeginnings 211 and 212. Likewise, a user can be informed that eventobject 205 c with the next closest end time was on a pink calendar (e.g.a calendar related to a child), with event objet 205 c being displayedon top of 205 b (but not extending downward as far) in FIGS. 2A and 2B.

As for event object 205 c, it no longer is displayed just at beginningedge 213, but now event object 205 c is shown to have an end time of 9AM. Additionally, event object 205 f is shown at beginning edge 213 tosignify that an event ends before 8:30 AM, and is this off-screen. Insome embodiments, in order to more clearly see overlapping eventobjects, one or more event objects can be shifted (e.g., to the right orthe left). As shown, event object 205 c has a left edge shifted to theright, so that a user can see event object 205 f. As mentioned above,such a shift can be performed when multiple event objects are displayedat an edge. In some embodiments, the number of event objects that arestacked can be limited to a predetermined number, such as two or three.For example, if a new event object reaches the edge, the event object onthe bottom (or top for the beginning edge) can be removed when the newevent object is added. As an alternative, the most recent event objectreaching the edge might simply disappear and not be added to the stack.

Event objects 205 g-205 j are also pointed out as these objects willbecome stacked in FIG. 2D. Event objects can also be shifted when twoevents occur at the same time. Event objects 205 h and 205 i are shownin a split view, where each occupies half of the column for Tuesday.

FIG. 2D shows a graphical user interface (GUI) with an earlier timerange for calendar window 200. The time range shown is between about12:00 AM and 12:00 PM, which corresponds to beginning 213 and ending223. Event objects 205 a, 205 b, and 205 f are now shown with start andend times viewable. However, event objects 205 h-205 j are now shownstacked on top of each other. The particular stacking shows that eventobject 205 j is from the blue calendar and has a starting time that isbefore the starting times of the other events in the stack. Eventobjects 205 h and 205 i still show the split view to indicate that thecorresponding events occur at the same time. Event objects 205 h and 205i are also displayed in a foreground of 205 j, but do not extend as highas 205 j, thereby enabling a user to view all three event objects. And,event object 205 g is shown at the bottom of the stack to indicate thatevent object on the pink calendar has a starting time that is the latestout of the four event objects in the stack. Note that embodiments arestill instructive even when only one color is used, or when stackedevents are form a same color-coded calendar. In one implementation, onlyfour pixels in height are shown for a clipped event object (e.g. fourpixels above or below the next event object in the stack), but otherimplementations could use more or less.

III. Method for Off-Screen Events

FIG. 3 is a flowchart illustrating a method 300 a method for displayingevents in a calendar application executing on a computer system. Thecomputer system may include one or more processors and a display, e.g.,an LCD display or a projector. The events can be displayed on a calendarwindow of the application, which can be accomplished by sending graphicsinformation to a graphics processor, which in turn sends signals to adisplay device.

In step 310, a plurality of events are optionally received at thecomputer system. For example, a user can specify start times and endtimes for an event, e.g., as described above. Alternatively, a user canspecify events on one device that is networked to a different device(each potentially part of a computer system that includes networkeddevices), and then send the events form one device to another. Any eventinformation can already be in the application, and thus does not need tobe received. In one aspect, each event includes a start time and an endtime for one or more days. As mentioned above, an event can repeat formultiple days in a week and/or across weeks.

In step 320, a calendar window is displayed on a display of the computersystem. The display can be any means for displaying a computer-generatedimage. The calendar window has a time range that is user-selectable,e.g., as shown in FIGS. 2A-2D. Various embodiments can allow the user toselect the time range in various ways, e.g., via scrolling or enteringthe desired values for the range. Thus, a user can change the time rangein order to view events at various times. In one implementation, thelength of the time range is fixed, and a user can shift the time rangeto cover different periods of a day. In another implementation, thelength of the time range is also variable. The displaying can beaccomplished by the calendar application by generating graphicsinformation for the calendar window and sending the graphics informationto a graphics processor.

In step 330, a first time range for the calendar window is received. Thetime range can be specified in various ways. The first time range can bespecified by the calendar application, e.g., as a default value or froma stored value of the time range last viewed when the calendarapplication was closed. The user can also specify the time range, e.g.,as described herein.

In step 340, a first event object corresponding to a first event that iswithin the first time range is displayed. The first event object canindicate a first start time and a first end time of the first event. Forexample, event object 205 a in FIG. 2D indicates a start time of 9 AMand an end time of 10 AM. Both of the first start time and the first endtime may be within a selected time range, e.g., as is shown for eventobject 205 a in FIG. 2D. Or, just one of the first start time or thesecond end time may be within the first time range. For example, eventobject 205 g in FIG. 2C has a start time within the selected time range,but the end time is not within the selected time range. As anotherexample, event object 205 c in FIG. 2C has an end time within theselected time range, but the start time is not within the selected timerange.

In step 350, the calendar window is changed to have a second time range.The second time range has a different beginning and/or ending valuecompared to the first time range. For some values of change the firstevent is outside the second time range. For example, the first starttime and the first end time of the first event are not within the newvalues specified for the second time range. The change from the firsttime range to the second time range can be continuous. For example, thetime range may go through multiple intermediate time ranges beforereaching the second time range. In various embodiments, the intermediatetime ranges can have any value between the two time ranges can beobtained, or the intermediate time ranges can move in specified timeincrements, such as 5, 10, 15, or 30 minute increments. The change intime ranges can also be a single time change, e.g., a user can enter thetimes for the time range and the display can immediately jump to thespecified time range.

In one embodiment, the calendar application checks where the ending edgeof the time range is at compared to the start time of events anddetermines if the event object is to be held at the ending edge.Similarly, the calendar application can check where the beginning edgeof the time range is at compared to the end time of events anddetermines if the event object is to be held at the ending edge.However, tracking every event object could be computationally demanding.Thus, one implementation can identify event objects that are within athreshold of the edges, and the calendar application can track locationsof these event objects in relation to the edges while the time range isscrolling.

In step 360, a part of the first event object is displayed at an edge ofthe calendar window to indicate that an event exists outside of thesecond time range of the calendar window. Normally, if an event is notwithin a specified range, a corresponding event object would not bedisplayed. However, embodiments continue to display the first eventobject, thereby providing additional information to the user, e.g., thatan event exists outside the selected time range, a number of off-screenevents in a particular direction (i.e. earlier or later than theselected time range), and which type of calendar the off-screen event isfrom (e.g. work or personal calendar).

In embodiments where the change is continuous, the beginning and endingof the time range of the calendar window can change in a continuousmanner. The start and end times of an event object can be tracked. Forexample, the ending of the time range reaching the first start time canbe identified. Then, a beginning part of the first event object (e.g., atop of the object) can be held at the ending of the time range as thetime range continues to change, as opposed to the first event objectcompletely disappearing. As another example, when the beginning of thetime range reaches the first end time can also be identified. Then, anending part of the first event object can be held at the beginning ofthe time range as the time range continues to change. Thus, the eventobject can stick within the viewable area of the calendar window evenafter the event itself moves outside of the current time range. Such atechnique can provide a seamless movement of objects on the screen, soas not to distract a user, and information about an event object can beretained once the event moves off-screen.

In one embodiment, the first start time or the first end time can bedisplayed as time values at the edge of the calendar window along withthe part of the first event object. In this manner, a user can identifymore information about the event not included in the selected timerange. Thus, a user could know when an event start, as opposed to justknowing that an event occurs later than the selected time range.

To indicate that more than one event occurs before or after the selectedtime range, the event objects may be stacked at a respective edge of thecalendar window. For example, a second event object corresponds to asecond event, where the second event includes a same day as the firstevent. For instance, both events occur on a particular Wednesday. A partof the second event object can continue to be displayed at the edge ofthe calendar window when the second event falls outside of the timerange of the calendar window at the edge. If the first event is afterthe second event, but both are outside of the selected time range, thesecond event could be displayed on top of the first event.

The stack can be created by displaying the first event object in aforeground and the second event object behind it, with the first eventobject being of smaller size than the second event object. In anotherembodiment, the part of the second event object that is displayed has abottom part that ends when the top part of the first event objectbegins, when stacked at the edge. In such an embodiment, both eventobjects can be displayed in the same layer. Both scenarios can generatea stack of event objects. To help see the different event objects of astack, the first event object and/or the second event object can beshifted when one of the first event object and the second event objectis displayed stacked on top of the other. For example, if a left edge ofan event object displayed in the foreground is shifted to the right, anevent object in the background can more easily be seen.

The number of event objects shown at an edge can be limited by apredetermined number. When a number of events objects that are displayedat the edge of the calendar window exceeds a predetermined number, oneof the event objects can be dropped, and not displayed any more. Forexample, if the predetermined number was three, suppose another eventobject becomes held at an edge where a stack of three event objects isalready held. Then, one of the event objects is dropped, e.g., the eventobject furthest from the edge, which can be the event with the earliestending event for the beginning edge of the time range and the lateststarting event for the ending edge of the time range. In one embodiment,if two events in the stack are from a same calendar (e.g. a personalcalendar), then one of those can be dropped in favor of an event from adifferent calendar.

In one embodiment, the viewable part of an event object can be tracked.For example, the event object can be displayed between a first boundaryand a second boundary. When the corresponding event is entirely withinthe selected time range, then the first boundary would correspond to thestart time of the event and the second boundary would correspond to theend time. In FIG. 2B, event object 205 g has the boundariescorresponding to the start and end times of the corresponding event,since the event is within the selected time range of beginning edge 212and ending edge 222.

As the selected time range changes to edges 213 and 223 in FIG. 2C, thesecond boundary deviates from the end time of the corresponding event.Specifically, when the second boundary reaches ending edge 223, thesecond boundary is held at the ending edge as that edge changes.Accordingly, as ending edge continues to become earlier in time, thesecond boundary of event object 205 g corresponds to the ending edge.The viewable part of the event object is thus visually compressed.Similarly, the first boundary can be held at the beginning edge if thetime range is moved in the other direction. The first boundary wouldthen be the initial boundary reaching an edge of the selected timerange.

The visual compression is stopped before the viewable part of the eventobject disappears. For example, when a size of the event object reachesa first predetermined value, the visual compression of the first eventobject is stopped. As shown in FIG. 2D, when the height of the displayedpart of event object 205 g reaches a certain value (e.g., four pixels inheight), the first boundary is held at a value that is four pixels abovethe second boundary. Thus, the compressed event object continues to bedisplayed even when both the start and end time of the correspondingevent are outside of the selected time range.

For stacking, the following event objects can have a differentpredetermined size. For instance, event object 205 i can have a heightthat is double the height of event object 205 g. But, since event object205 g is in a top layer, only part of event object 205 g is actuallydisplayed. In this manner, the viewable part of both event objects isabout the same. Other embodiments could have the viewable parts differ.A similar technique can be used for stacking at the beginning boundary.

In another embodiment for stacking, the initial (leading) boundary ofthe following event object (e.g. event object 205 i) could be held atthe first boundary of the first event object (e.g., event object 205 g),instead of being held at the ending edge 224. In this manner, differentlayers are not needed. However, such a technique can have display issueswhen the viewable parts have curves, which would cause some horizontalpixels to have different boundaries, as is shown. Such problems could becured by having the boundaries being defined for each horizontal pixelso that the leading boundary is held at the boundary value define forthat horizontal pixel.

The concept of showing indicators of off-screen events can also be usedto show interday information. For example, if a user is trying toschedule a meeting and is only viewing one day (e.g. as the viewing ison a handheld device), then the calendar window can indicate if an eventon a previous or next day has an event at a particular block of time,e.g., by hour. Or, as an alternative, an indication of no event can beprovided. Such indicators could simply be arrows or other objects, whichare separate from the event objects.

IV. Alternative User Interfaces for Off-Screen Events

For some people, it may be difficult to identify whether an event objectdisplayed at the edge of the calendar window is indicating an off-screenevent or whether the start time (or end time) is just very close to theedge of the time range. Accordingly, some embodiments can modify theevent object to indicate the difference. For example, the width of theevent object could be reduced once the event falls outside of a timerange. In one implementation, the computer system can track when a starttime of an event objects reaches the ending edge of the time range, andmodify the event object at that time. As another example, the eventobjet can be rotated.

FIG. 4 shows a graphical user interface (GUI) for viewing a calendarapplication where an event object is rotated at an edge of the calendarwindow 400 according to embodiments of the present invention. Calendarwindow 400 is similar features as calendar window 200, with a time rangeon the vertical axis and different days of a week on a horizontal axis.The selected time range runs between just before 7:30 AM to just before7:30 PM.

As shown, a part of event objects 405 a and 405 b are displayed at anedge of calendar window 400 to indicate off-screen events. These eventobjects have start times of 7:30 PM and 10 PM, respectively. To showthat event objects 405 a and 405 b are indicating an off-screen eventand not an on-screen (i.e. within the selected time range), eventobjects 405 a and 405 b are rotated. As shown, the rotation isclockwise, but counterclockwise rotation can also be used. As anexample, event objects for off-screen events at the beginning edge ofthe time range could be rotated in one direction, and the events objectsfor off-screen events at the ending edge of the time range could berotated in the other direction.

As mentioned above, there can be two off-screen events in the samedirection for a particular day. In embodiments mentioned above, suchevent objects may be stacked, e.g., to show a number of off-screenevents occurring before the beginning edge or after the ending edge.Such stacking can also be used when the event objects are rotated. Therelative times for these event objects indicating off-screen events canalso be indicated by the positions in the stack, as described above.

In another embodiment, the rotated events objects could be displayedside-by-side, or at least shifted in some manner with some overlap.Thus, a top corner (or bottom corner when the beginning edge isinvolved) of each event object at the edge could be at a differentlocation on the horizontal axis. In order to indicate a relative time,the top (for ending edge) or bottom (for beginning edge) of the cornersof the event objects could be used, as for embodiments using a stack. Inanother implementation, a time can be displayed for each modified eventobject. As shown, a starting time is shown as a time value in the topcorner for event objects 405 a and 405 b. For event objects at thebeginning edge, the ending time could be displayed.

Accordingly, various embodiments can provide an indication of an eventthat is off screen (outside of a selected time range) using a same eventobject that is used when the event does fall within the selected timerange. Such use of the event object provides a seamless display forproviding information about the event object, and can indicate whichcalendar the even belongs to, among other information conveyed by theevent object. Further, the display of multiple event objects at an edgeof a calendar window can convey that multiple events are off-screen.

V. Navigating Week View

Typical calendar applications have two methods for navigating whenviewing a week. One can scroll one week at a time or scroll one day at atime, where each has inherent limitations. Embodiments can combineaspects of scrolling by day and scrolling by week into a hybrid approachthat includes advantages of both. In one embodiment, a new navigationmechanism navigates in the week view by keeping today (or other selectedday) at the left most column. For example, the week can be displayedwith the current day first (e.g. in the left most column), therebyproviding a more relevant view to a user. Then, when a user selects tomove forward or backward, the next or previous full week (i.e. startingwith a designated day, such as Sunday or Monday) can be displayed. And,when a user forward through the current day (or other selected day), theweek view can stop with the selected day displayed first, to give a usera view of the next set of days following the selected day.

A. Setup

FIG. 5 shows a graphical user interface (GUI) 510 for providing setupinformation for navigating a calendar window 500 according toembodiments of the present invention. In GUI 510, a user can definewhich days are to be displayed, the functionality of navigation buttons,and how events are displayed. GUI 510 allows settings to be selected,and is an example of a setting interface.

Picklist 520 (also called a dropdown menu) may be used to select howmany days are displayed for a week. In some embodiments, the two optionsare five days (e.g., Monday through Friday of the standard workweek inthe Unites States) and seven days of the standard full week. In otherembodiments, a week can be defined as including 3, 4, or 6 sequentialdays, which may be consecutive days or non-consecutive days, e.g.,Monday, Wednesday, and Friday are still sequential but no consecutive.

Picklist 530 may be used to determine the start (boundary) day of aweek. The boundary day can be used as a default day for displaying firstwhen displaying a week in a calendar window. For example, definingSunday to be the boundary day can result in Sunday being displayed in aleft most column of a week view in a calendar. When less than seven daysare chosen to be in a week, the options for a start day be may bereduced to be less than all seven days of the standard week.

Picklist 540 allows a user to define how to navigate in week view. Inone embodiment, there are three options: day, week, and auto. The dayoption moves the calendar by one day at a time (e.g., advances one dayor reverses one day). The week option moves the calendar from theboundary day of one week being displayed first (e.g. left most column)to the boundary day of the next week. With the “auto” option, a hybridnavigation scheme can be provide, and other days of the week can bedisplayed first, as is described below.

Picklist 550 can allow a user to define when a day starts, e.g., a workday. Picklist 560 can allow a user to define when a day ends, e.g., theend of the work day. These values can determine shading in the calendarwindow and how an event object (as described above) is displayed whenthe corresponding event is all day. Picklist 570 allows a user tospecify how many hours are shown in the calendar window. For example, auser can specify that 12 hours is shown as a fixed time length of avariable time range of the calendar window.

FIG. 6 shows a graphical user interface (GUI) 610 for selecting optionsfor how to scroll in week view for calendar window 600 according toembodiments of the present invention. Picklist 640 is shown open, andthe “auto” option be selected.

B. Basic Operation

FIG. 7 is a flowchart illustrating a method 700 for navigating acalendar application executing on a computer system according toembodiments of the present invention. Although embodiments are describedwith respect to a week view, embodiments are applicable to other viewsof multiple days, such as a month view or any other suitable view of aplurality of days.

In step 710, a first week is displayed in a calendar window. Forexample, FIG. 8A shows a calendar window 800 of a week view startingwith Sunday. Buttons 820 (examples of view objects) may be used toselect a day view, week view (shown selected), month view, or year view.The week view is shown.

As shown, the left most column corresponds to the day that is displayedfirst. The following days then appear in consecutive columns to theright. Other displays are possible, e.g., a right to left display, or anup and down display. The displaying can be accomplished by the calendarapplication by generating graphics information for the calendar windowand sending the graphics information to a graphics processor, as wasmentioned above for method 300.

Herein, a week is any set of N sequential days, where N is greater thanone. As mentioned above, the displayed seven days can start at any day.For example, the first week could start on a Sunday (as is normal in theUnites Sates), which may be the default for the application. Otherdefault values could have a week starting on Monday or Saturday, as iscommon in other countries.

In step 720, a selection of a day in the first week is received. Theselected day is not displayed first in the calendar window. Thus, if thefirst displayed day is Sunday, the selected day is not Sunday. In FIG.8A, the selected day 810 is Tuesday, and is highlighted.

The day may be selected in various ways. For example, the selected daycan correspond to today as a default. The calendar application can keeptrack of the current day (i.e. today), or the calendar application canreceive the current day from a module of another application. As anotherexample, a user can specify the selected day. For instance, a user canclick on a particular day, enter text into a box to select a day, or anyother suitable selection interface may be used.

In step 730, a user input to advance the calendar by a week is received.The user input can be provided in various ways. FIG. 8A shows buttons830 (examples of navigation objects) for navigating in the week view.The forward button (shown behind the cursor) can be used to advance thedays shown in the calendar window. The back button can be used toreverse (rewind) the days shown in the calendar window. In oneembodiment, the “today” button is used to display today first, e.g., inthe left most column, as is described in more detail later.

In step 740, the calendar window is advanced such that the selected dayis displayed first in the calendar window. Thus, although the user hasselected to advance the calendar window by a week, the calendarapplication advances the calendar window only by the number of days tomake the selected day appear first in the calendar window.

FIG. 8B shows a calendar window 850 after the forward button 831 hasbeen selected by a user while the “auto” setting has been selected frompicklist 640. In FIG. 8A, Sunday January 29^(th) was shown in the leftmost column. In other situations as shown below, selecting forwardbutton 831 will cause calendar window to advance seven days. But, sinceTuesday January 31 was selected (e.g., because that is the date oftoday), the calendar window only advances enough days (specifically two)to display Tuesday in the left most column. In this manner, a user willsee the events of the next seven days.

C. Advanced Functionality

Besides stopping advancement of the calendar window when the left columnhits the selected day (e.g., today), the navigation in week view candiffer in other ways from a basic seven day advancement and reversal.For example, when the selected day is displayed first, and the selectedday is not the boundary day, then the forward button will cause the nextboundary to be displayed at the left column. The selected day (e.g.today) and the boundary are independent of each other, and may be chosento be the same or different. This feature and others are now described.

FIG. 9 is a flowchart illustrating a method 900 for determining how tochange the days displayed in a calendar window in response to a userinput according to embodiments of the present invention. Method 900addresses when the user input is to advance or reverse the daysdisplayed in the calendar while in week view. Method 900 refers to“today”, but is equally applicable to the selected day being determinedin other ways, as described herein. Also, the description assumes thatthe day being displayed first is in the left most column, but otherarrangements of the days (e.g. right to left) can be used.

In step 910, the calendar application executing on a computer systemwaits for user input. The user input can be provided in any of the waysdescribed herein. In step 920, the user input is received, e.g., a usermay have clicked a navigation arrow (back arrow 832 or forward arrow831) or swiped their fingers across the display in a forward or backwardmotion.

In step 930, it is determined whether the gesture (i.e. the user input)is to go back in time (i.e. reverse the days). If the gesture was not togo back in time, method 900 proceeds to step 940, which determineswhether the gesture was to go forward in time. If the gesture was notforward in time, then nothing happens at step 941. If the gesture was togo forward in time, then method 900 proceeds to step 950.

In step 950, it is determined whether today (or other selected day) isin the currently displayed week and not displayed first (e.g. in theleft most column). If today is displayed in the current week but notfirst, then the calendar window is advanced so that today is displayedfirst (e.g., in the left most column) at step 951. This examplecorresponds to the calendar window depicted in FIG. 8A, and the resultis depicted in FIG. 8B as calendar window 850. If the criteria of step950 is not satisfied, then the calendar window is advanced such that thestart day (i.e. boundary day) of the next week is displayed first atstep 952. FIG. 8B shows calendar window 850 not satisfying the criteria,since today is displayed first. FIG. 10A shows a calendar window 1000resulting from a forward gesture, as now the next Sunday, February 5, isshown in the left most column. If the user provides another forwardgesture, then the calendar window would also change according to step952, and thus Sunday February 12 would be in the left most column.

If the gesture was to go back in time, method 900 proceeds to step 931,where it is determined if today (or other selected day) is currentlydisplayed in the left most column. If today is not displayed in the leftmost column, then it is determined whether today is part of the previousweek. If today is in the previous week, then today is displayed in theleft most column at step 933 (which more generally corresponds to theselected day is displayed first). This example corresponds to calendarwindow 1000 of FIG. 10A, and the resulting calendar window 850 is shownin FIG. 8B. If today is not part of the previous week, then the start ofthe previous week is displayed first at step 934. For example, if onegestures backward for calendar window 800 in FIG. 8A, then the resultingcalendar window is calendar window 1010 of FIG. 10B, since the selectedday (Tuesday January 31) is not in the left column and not in theprevious week.

If today is in the left most column, then method 900 proceeds to step935, which determined whether today is the start of the week. If todayis the start of the week, then the start of the previous week isdisplayed at step 937. For example, if today is Sunday (and Sunday wasdesignated as the start of the week), then a back gesture will cause thecalendar window to move so that the previous Sunday is in the left mostcolumn. If today is not the start of the week, then the start of thecurrent week is displayed in the left most column at step 936. Forexample, if one gestures backward for calendar window 850 in FIG. 8B,then the resulting calendar window is calendar window 800 of FIG. 10A,since the selected day (Tuesday January 31) is displayed first and isnot designated as the start of the week.

Additionally, a navigation object 833 of FIG. 8B can be used to changethe calendar window so that Today is displayed first. Thus, wherever auser is at in the calendar, clicking the Today button will move the weekview to show Today first followed by the next set of days (e.g. the nextsix days). For example, if one were at the calendar window in FIG. 10A,selecting navigation object 833 will cause the calendar window in FIG.8B to be displayed.

In one embodiment, when the computer system launches the Calendarapplication, it starts with today on the left most column. If a userclicks the next arrow, the calendar advances to the next start of weekboundary (ex: Sunday). If a user clicks the next arrow again, it'llscroll by week to the next week boundary. From then on, the navigationis one week at a time. If a user presses the back button, it'll navigateone week at a time, until the calendar enters the current week, where itwill stop on Today and keep Today on the left most column. If a userclicks the back button the calendar will go to the start of the currentweek. From then on, clicking the back button navigates one week at atime. This navigation mechanism is similar to the mechanism ofnavigating one week at a time, but has the extra advantage of alwaysstopping on Today when you enter the current week.

Additional features can include: if a user leaves the applicationrunning overnight, the application can navigate itself one day forwardby preserving the current day on the left column. Also, if a userlaunches the application the next day, the application willautomatically start with today on the left most column. Another featurecan include: regardless of what days are displayed in the application,clicking on the today button displays today on the left most column.

VI. Computer System

Any of the computer systems mentioned herein may utilize any suitablenumber of subsystems. Examples of such subsystems are shown in FIG. 11in computer apparatus 1100. In some embodiments, a computer systemincludes a single computer apparatus, where the subsystems can be thecomponents of the computer apparatus. In other embodiments, a computersystem can include multiple computer apparatuses, each being asubsystem, with internal components.

The subsystems shown in FIG. 11 are interconnected via a system bus1175. Additional subsystems such as a printer 1174, keyboard 1178, fixeddisk 1179, monitor 1176 (or other display), which is coupled to displayadapter 1182, and others are shown. Displaying of the calendar windowand other graphical objects can be accomplished by the calendarapplication executing on the central processor to generate graphicsinformation for the calendar window and send the graphics information tothe display adapter (which can include a graphics processor) forrendering an image.

Peripherals and input/output (I/O) devices, which couple to I/Ocontroller 1171, can be connected to the computer system by any numberof means known in the art, such as serial port 1177. For example, serialport 1177 or external interface 1181 (e.g. Ethernet, Wi-Fi, etc.) can beused to connect computer system 1100 to a wide area network such as theInternet, a mouse input device, or a scanner. The interconnection viasystem bus 1175 allows the central processor 1173 to communicate witheach subsystem and to control the execution of instructions from systemmemory 1172 or the fixed disk 1179, as well as the exchange ofinformation between subsystems. The system memory 1172 and/or the fixeddisk 1179 may embody a computer readable medium. Any of the valuesmentioned herein can be output from one component to another componentand can be output to the user.

A computer system can include a plurality of the same components orsubsystems, e.g., connected together by external interface 1181 or by aninternal interface. In some embodiments, computer systems, subsystem, orapparatuses can communicate over a network. In such instances, onecomputer can be considered a client and another computer a server, whereeach can be part of a same computer system. A client and a server caneach include multiple systems, subsystems, or components.

It should be understood that any of the embodiments of the presentinvention can be implemented in the form of control logic using hardware(e.g. an application specific integrated circuit or field programmablegate array) and/or using computer software with a generally programmableprocessor in a modular or integrated manner. Based on the disclosure andteachings provided herein, a person of ordinary skill in the art willknow and appreciate other ways and/or methods to implement embodimentsof the present invention using hardware and a combination of hardwareand software.

Any of the software components or functions described in thisapplication may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructionsor commands on a computer readable medium for storage and/ortransmission, suitable media include random access memory (RAM), a readonly memory (ROM), a magnetic medium such as a hard-drive or a floppydisk, or an optical medium such as a compact disk (CD) or DVD (digitalversatile disk), flash memory, and the like. The computer readablemedium may be any combination of such storage or transmission devices.

Such programs may also be encoded and transmitted using carrier signalsadapted for transmission via wired, optical, and/or wireless networksconforming to a variety of protocols, including the Internet. As such, acomputer readable medium according to an embodiment of the presentinvention may be created using a data signal encoded with such programs.Computer readable media encoded with the program code may be packagedwith a compatible device or provided separately from other devices(e.g., via Internet download). Any such computer readable medium mayreside on or within a single computer program product (e.g. a harddrive, a CD, or an entire computer system), and may be present on orwithin different computer program products within a system or network. Acomputer system may include a monitor, printer, or other suitabledisplay for providing any of the results mentioned herein to a user.

Any of the methods described herein may be totally or partiallyperformed with a computer system including one or more processors, whichcan be configured to perform the steps. Thus, embodiments can bedirected to computer systems configured to perform the steps of any ofthe methods described herein, potentially with different componentsperforming a respective steps or a respective group of steps. Althoughpresented as numbered steps, steps of methods herein can be performed ata same time or in a different order. Additionally, portions of thesesteps may be used with portions of other steps from other methods. Also,all or portions of a step may be optional. Additionally, any of thesteps of any of the methods can be performed with modules, circuits, orother means for performing these steps.

The specific details of particular embodiments may be combined in anysuitable manner without departing from the spirit and scope ofembodiments of the invention. However, other embodiments of theinvention may be directed to specific embodiments relating to eachindividual aspect, or specific combinations of these individual aspects.

The above description of exemplary embodiments of the invention has beenpresented for the purposes of illustration and description. It is notintended to be exhaustive or to limit the invention to the precise formdescribed, and many modifications and variations are possible in lightof the teaching above. The embodiments were chosen and described inorder to best explain the principles of the invention and its practicalapplications to thereby enable others skilled in the art to best utilizethe invention in various embodiments and with various modifications asare suited to the particular use contemplated.

A recitation of “a”, “an” or “the” is intended to mean “one or more”unless specifically indicated to the contrary. All patents, patentapplications, publications, and descriptions mentioned above are hereinincorporated by reference in their entirety for all purposes. None isadmitted to be prior art.

What is claimed is:
 1. A method of navigating a calendar applicationexecuting on a computer system, the method comprising: displaying afirst week in a week view of a calendar on a display of the computersystem, including a first boundary day for the first week, wherein theweek view displays three or more sequential days; receiving a selectionof a particular day in the first week; while displaying the first week,receiving an input to advance the week view of the calendar; and, inresponse to receiving the input to advance the week view of thecalendar, advancing the week view of the calendar by an amount that isdetermined based on which day of the week was selected in the receivedselection of the particular day, wherein the advancing includes: inaccordance with a determination that the particular day is the firstboundary day, displaying a second week in the week view of the calendar,distinct from the first week, wherein the second week comprises a secondboundary day that corresponds to a same day-of-the-week as the firstboundary day; and in accordance with a determination that the particularday is not the first boundary day, displaying a third week in the weekview of the calendar, wherein the third week comprises a third boundaryday that is the particular day; wherein a respective boundary daycorresponds to the day-of-the-week displayed first in a sequence of daysdisplayed in the week view in the calendar.
 2. The method of claim 1,including: while displaying the first week, receiving an input toreverse the week view of the calendar; and in response to receiving theinput to reverse the week view: determining whether the particular dayis displayed as the first day in the week view of the first week; inaccordance with a determination that the particular day is displayed asthe first day in the week view of the first week: determining whetherthe particular day corresponds to a predefined first day-of-the-week; inaccordance with a determination that the particular day corresponds tothe predefined first day-of-the-week, displaying a fourth week in theweek view, wherein the fourth week is one week earlier than the firstweek and starts on the same day-of-the-week as the particular day; inaccordance with a determination that the particular day does notcorrespond to the predefined first day-of-the-week, displaying a fifthweek in the week view, wherein the fifth week starts on the predefinedfirst day-of-the-week preceding the particular day.
 3. The method ofclaim 2, including: in response to receiving the input to reverse theweek view, in accordance with a determination that the particular day isnot displayed as the first day in the week view of the first week:determining whether the particular day is in the week preceding thefirst week; in accordance with a determination that the particular dayis in the week preceding the first week, displaying a sixth week in theweek view, wherein the sixth week starts on the particular day; and, inaccordance with a determination that the particular day is not in theweek preceding the first week, displaying a seventh week in the weekview, wherein the seventh week starts on the predefinedfirst-day-of-the-week of the week preceding the first week.
 4. Themethod of claim 1, wherein the selection of the particular day isreceived from a module running on the computer system that determines acurrent day.
 5. The method of claim 1, wherein the selected daycorresponds to the current day.
 6. The method of claim 1, wherein theselected day corresponds to a user-selected day-of-the-week.
 7. Anelectronic device, comprising: a display; one or more processors;memory; and one or more programs, wherein the one or more programs arestored in the memory and configured to be executed by the one or moreprocessors, the one or more programs including instructions for:displaying a first week in a week view of a calendar on a display of thecomputer system, including a first boundary day for the first week,wherein the week view displays three or more sequential days; receivinga selection of a particular day in the first week; while displaying thefirst week, receiving an input to advance the week view of the calendar;and, in response to receiving the input to advance the week view of thecalendar, advancing the week view of the calendar by an amount that isdetermined based on which day of the week was selected in the receivedselection of the particular day, wherein the advancing includes: inaccordance with a determination that the particular day is the firstboundary day, displaying a second week in the week view of the calendar,distinct from the first week, wherein the second week comprises a secondboundary day that corresponds to a same day-of-the-week as the firstboundary day; and in accordance with a determination that the particularday is not the first boundary day, displaying a third week in the weekview of the calendar, wherein the third week comprises a third boundaryday that is the particular day; wherein a respective boundary daycorresponds to the day-of-the-week displayed first in a sequence of daysdisplayed in the week view in the calendar.
 8. The electronic device ofclaim 7, further including instructions for: while displaying the firstweek, receiving an input to reverse the week view of the calendar; andin response to receiving the input to reverse the week view: determiningwhether the particular day is displayed as the first day in the weekview of the first week; in accordance with a determination that theparticular day is displayed as the first day in the week view of thefirst week: determining whether the particular day corresponds to apredefined first day-of-the-week; in accordance with a determinationthat the particular day corresponds to the predefined firstday-of-the-week, displaying a fourth week in the week view, wherein thefourth week is one week earlier than the first week and starts on thesame day-of-the-week as the particular day; in accordance with adetermination that the particular day does not correspond to thepredefined first day-of-the-week, displaying a fifth week in the weekview, wherein the fifth week starts on the predefined firstday-of-the-week preceding the particular day.
 9. The electronic deviceof claim 8, further including instructions for: in response to receivingthe input to reverse the week view, in accordance with a determinationthat the particular day is not displayed as the first day in the weekview of the first week: determining whether the particular day is in theweek preceding the first week; in accordance with a determination thatthe particular day is in the week preceding the first week, displaying asixth week in the week view, wherein the sixth week starts on theparticular day; and, in accordance with a determination that theparticular day is not in the week preceding the first week, displaying aseventh week in the week view, wherein the seventh week starts on thepredefined first-day-of-the-week of the week preceding the first week.10. The electronic device of claim 7, wherein the selection of theparticular day is received from a module running on the computer systemthat determines a current day.
 11. The electronic device of claim 7,wherein the selected day corresponds to the current day.
 12. Theelectronic device of claim 7, wherein the selected day corresponds to auser-selected day-of-the-week.
 13. A non-transitory computer readablestorage medium storing one or more programs, the one or more programscomprising instructions, which when executed by an electronic devicewith a display, and a touch-sensitive surface, cause the device to:display a first week in a week view of a calendar on a display of thecomputer system, including a first boundary day for the first week,wherein the week view displays three or more sequential days; receive aselection of a particular day in the first week; while displaying thefirst week, receive an input to advance the week view of the calendar;and, in response to receiving the input to advance the week view of thecalendar, advance the week view of the calendar by an amount that isdetermined based on which day of the week was selected in the receivedselection of the particular day, wherein the advancing includes: inaccordance with a determination that the particular day is the firstboundary day, display a second week in the week view of the calendar,distinct from the first week, wherein the second week comprises a secondboundary day that corresponds to a same day-of-the-week as the firstboundary day; and in accordance with a determination that the particularday is not the first boundary day, display a third week in the week viewof the calendar, wherein the third week comprises a third boundary daythat is the particular day; wherein a respective boundary daycorresponds to the day-of-the-week displayed first in a sequence of daysdisplayed in the week view in the calendar.
 14. The non-transitorycomputer readable storage medium of claim 13, further includinginstructions that cause the device to: while displaying the first week,receive an input to reverse the week view of the calendar; and inresponse to receiving the input to reverse the week view: determinewhether the particular day is displayed as the first day in the weekview of the first week; in accordance with a determination that theparticular day is displayed as the first day in the week view of thefirst week: determine whether the particular day corresponds to apredefined first day-of-the-week; in accordance with a determinationthat the particular day corresponds to the predefined firstday-of-the-week, display a fourth week in the week view, wherein thefourth week is one week earlier than the first week and starts on thesame day-of-the-week as the particular day; in accordance with adetermination that the particular day does not correspond to thepredefined first day-of-the-week, display a fifth week in the week view,wherein the fifth week starts on the predefined first day-of-the-weekpreceding the particular day.
 15. The non-transitory computer readablestorage medium of claim 14, further including instructions that causethe device to: in response to receiving the input to reverse the weekview, in accordance with a determination that the particular day is notdisplayed as the first day in the week view of the first week:determining whether the particular day is in the week preceding thefirst week; in accordance with a determination that the particular dayis in the week preceding the first week, displaying a sixth week in theweek view, wherein the sixth week starts on the particular day; and, inaccordance with a determination that the particular day is not in theweek preceding the first week, displaying a seventh week in the weekview, wherein the seventh week starts on the predefinedfirst-day-of-the-week of the week preceding the first week.
 16. Thenon-transitory computer readable storage medium of claim 13, wherein theselection of the particular day is received from a module running on thecomputer system that determines a current day.
 17. The non-transitorycomputer readable storage medium of claim 13, wherein the selected daycorresponds to the current day.
 18. The non-transitory computer readablestorage medium of claim 13, wherein the selected day corresponds to auser-selected day-of-the-week.